Method and apparatuses for influencing the invoking of a service provided by an application server to a user equipment

ABSTRACT

A server and method are described herein that can influence the invoking of a service provided by an application server to a user-user equipment. The server includes a database that stores a service profile for the user-user equipment, where the service profile has a number of filter criteria wherein at least one includes: (1) a first trigger point and at least one first service point trigger that specifies one or more conditions which when satisfied will be downloaded to and checked by a remote control function before a service is invoked for the user-user equipment; and (2) a second trigger point and at least one second service point trigger that specifies one or more conditions which are checked against internally stored data associated with the user-user equipment and need to be satisfied before the service profile with the filter criteria including the first trigger point and the at least one first service point trigger is downloaded to and checked by the remote control function to invoke the service for the user-user equipment.

CROSS REFERENCE TO RELATED APPLICATION

This application is the U.S. national phase of International ApplicationNo. PCT/IB2008/000587, filed 13 Mar. 2008, which designated the U.S. andclaims the benefit of U.S. Provisional Patent Application No. 60/946,187filed on Jun. 26, 2007 the contents of each of which are herebyincorporated by reference herein.

TECHNICAL FIELD

The present invention relates to the communications field and, inparticular, to a server (e.g., HSS) and a method for enabling the serverto influence the invoking of a service (e.g., IMS service) provided byan application server (e.g., IMS application server) to a user-userequipment (UE).

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description of the prior art andthe present invention.

-   3GPP 3rd Generation Partnership Project-   CAMEL Customized Applications for Mobile Networks Enhanced Logic-   CS Circuit Switched-   CSCF Call Session Control Function-   GUP Generic User Profile-   HSS Home Subscriber Server-   IP Internet Protocol-   IP-CAN IP Connectivity Access Network-   IM IP Multimedia-   IMS IP Multimedia Subsystem-   LTE Long Term Architecture-   PS Packet Switched-   PPA Push-Profile-Answer-   PPR Push-Profile-Request-   SAA Server-Assignment-Answer-   SAR Server-Assignment-Request-   S-CSCF Serving CSCF-   SDP Session Description Protocol-   SIP Session Initiation Protocol-   UE User Equipment-   UML Unified Modeling Language-   URI Uniform Resource Identifier-   WLAN Wireless Local Area Network

Referring to FIG. 1 (PRIOR ART), there is a diagram illustrating a 3GPPnetwork 100 which has a traditional HSS 102 that is coupled to a CSdomain 104, a PS domain 106 and an IM CN subsystem 108. The 3GPP network100 is described in detail within the 3GPP TS 29.228 V7.5.0 entitled“3rd Generation Partnership Project; Technical Specification Group CoreNetwork and Terminals; IP Multimedia (IM) Subsystem Cx and DxInterfaces; Signalling Flows and Message Contents (Release 7)”, datedMarch 2007 (the contents of which are incorporated by reference herein).As such, those skilled in the art are familiar with the architecture andfunctionality of this particular 3GPP network 100. Thus, for clarity,only the HSS 102 and the IM CN subsystem 108 (in particular a CSCF 110and an application server 112) which are relevant to the presentdiscussion are discussed in detail herein while the other well knowncomponents like the GMSC, MSC/VLR, SGSN, GGSN, OSA SCS, IM-SSF etc. . .. are not discussed in detail within this document. The CSCF 110 is theentity within the IM CN subsystem 108 that is involved in establishinguser call/sessions with UEs 114 (only one shown). The application server112 is the entity within the IM CN subsystem 108 that provides an IMSservice to the UE 114.

The HSS 102 has a master database 103 which stores information relatedto the users and their respective UEs 114 in the 3GPP network 100. Forthe sake of simplicity, user and user equipment are generally referredto as the same and have often been identified as UE 114 throughout thepresent document, so that the information stored in the master database103 on a user basis is generally referred to as user data irrespectiveof whether such data is associated with the user or their respectiveuser equipment. For instance, the HSS 102 incorporates the 2G/3G Corenetwork HLR functions in addition to other functions related to accesseslike the user control IP Multimedia Subsystem (IMS) functions, CSfunctions, PS functions, WLAN functions etc. . . . In particular, theHSS 102 supports the following functions: (1) mobility management; (2)user security information generations; (3) user security support; (4)service provisioning support; (5) call/session establishment support;(6) GUP data repository; (7) identification handling; (8) serviceauthorization support; (9) access authorization; (10) applicationservices support; and (11) CAMEL services support. Basically, the HSS102 has become a privileged point in the 3GPP network 100 where manydifferent accesses meet.

The traditional HSS 102 also has multiple tasks and one of those tasksis to handle the service profile 116 for the IMS UE 114 which receivesan IMS service from the IM application server 112. For instance, the HSS102 downloads the service profile 116 to a serving CSCF 110 (hereinafterS-CSCF and in particular the S-CSCF 110) assigned for serving the UE 114when the UE 114 registers with the IM CN subsystem 108. The S-CSCF 110then uses the service profile 116 to invoke the IMS service for the UE114. The HSS 102 would also download the service profile 116 to theS-CSCF 110 whenever an operator administratively changes data related tothe UE 114. A discussion about the contents of the traditional serviceprofile 116 is provided next but for a more detailed discussion aboutthe traditional service profile 116 reference is made to Annex B in theaforementioned 3GPP TS 29.228 V7.5.0

Referring to FIG. 2A (PRIOR ART), there is a diagram illustrating anoutline of a UML model for the traditional service profile 116 that iscurrently specified in 3GPP TS 29.228 V7.5.0. As shown, the traditionalservice profile 116 has the following: (1) a Public Identification class202; (2) a Core Network Service Authorization class 204; (3) an Initial.Filter Criteria class 206; and (4) a Shared IFC Set class 208. The IFCclass 206 is relevant to the present discussion because it contains themechanisms that are used by the S-CSCF 110 to invoke the IMS service forthe UE 114. Thus, the IFC class 206 is described in detail below whilethe Public Identification class 202, the Core Network ServiceAuthorization class 204, and the Shared IFC Set class 208 will not bediscussed in detail within this document.

Referring to FIG. 2B (PRIOR ART), there is a diagram illustrating anoutline of the UML model of the IFC class 206 currently specified in3GPP TS 29.228 V7.5.0. The IFC class 206 has zero to n IFC instances206′ (one shown) each of which is composed of zero or one instance of aTrigger Point class 210 and one instance of an Application Server class212. Each IFC 206′ has a priority attribute that indicates the priorityof the filter criteria where the higher the priority number then thelower the priority of the filter criteria. For example, an IFC 206′ witha higher value of priority number would be assessed after the IFC 206′with a smaller priority number has been assessed. Plus, each IFC 206′has a ProfilePartIndicator attribute that is an enumerated type, withpossible values “REGISTERED and UNREGISTERED”, which indicates if therespective filter is a part of the registered or unregistered userservice profile 116.

The Trigger Point class 210 describes trigger points that are checked bythe S-CSCF 110 to find out if the indicated application server 112 (forexample) should be contacted or not to provide an IMS service to the UE114. Each trigger point 210 is composed of 1 to n instances of theService Point Trigger class 214 (hereinafter SPT or SPT class). Plus,each trigger point 210 is a boolean expression in Conjunctive orDisjunctive Normal form (CNF of DNF). In particular, each trigger point210 has a ConditionTypeCNF attribute that defines how the set ofcorresponding SPTs 214 are expressed, i.e. either an ORed set of ANDedsets of SPT statements or an ANDed set of ORed sets of statements. Thesecombinations are termed, respectively, Disjunctive Normal Form (DNF) andConjunctive Normal Form (CNF). Both DNF and CNF forms can be used. Inthe absence of a trigger point class 210, this would indicate anunconditional triggering of the indicated application server 112.

The Application Server class 212 indicates the application server 112(for example), which is contacted, if the trigger points 210 and SPTs214 are met. The Application Server class 212 has a ServerName attributewhich contains the SIP URL of the application server 112 (for example).The Application Server class 212 also has a Default Handling attributewhich indicates whether the dialog with the UE 114 should be released ifthe application server 112 could not be reached. The Default Handlingattribute is enumerated and can take the values: SESSION_CONTINUED orSESSION_TERMINATED. In addition, the Application Server class 212contains zero or one instance of a Service Information class 216. TheService Information class 216 has a ServiceInfo attribute and allows thedownload of information to the S-CSCF 110 where the downloadedinformation is to be transferred transparently to an application server112 when the trigger points 210 of the corresponding IFC 206′ aresatisfied.

Referring to FIG. 2C (PRIOR ART), there is a diagram illustrating anoutline of an UML model of the SPT class 214 currently specified in 3GPPTS 29.228 V7.5.0. The SPT class 214 has one to n SPT instances 214′ (oneshown) where each SPT 214′ has a Group attribute that allows thegrouping of SPTs that will configure the sub-expressions inside a CNF orDNF expression. For instance, in the following CNF expression(A+B)·(C+D), A+B and C+D would correspond to different groups. In CNF,the Group attribute identifies the ORed sets of SPT instances 214′. Ifthe SPT 214′ belongs to different ORed sets, then that SPT 214′ can havemore than one Group value assigned. At least one Group is assigned foreach SPT 214′. In DNF, the Group attribute identifies the ANDed sets ofSPT instances 214′. If the SPT 214′ belongs to different ANDed sets,then that SPT 214′ can have more than one Group value assigned. At leastone Group is assigned for each SPT instance 214′. Plus, each SPT 214′also has a ConditionNegated attribute which defines whether thecorresponding instance is negated (i.e. NOT logical expression). Plus,each SPT 214′ has a RegistrationType attribute which is relevant only tothe SIP Method 216 (discussed below) that has a value of “REGISTER”(note: the support of the RegistrationType attribute is optional in theHSS 102 and in the S-CSCF 110).

Moreover, each SPT 214′ includes the following: (1) Request-URI class218; (2) SIP Method class 216; (3) SIP Header class 220; (4) SessionCase class 222; and (5) Session Description class 224. The Request-URIclass 218 contains a RequestURI attribute and defines a SPT for theRequest-URI. The SIP Method class 216 contains a Method attribute anddefines a SPT for the SIP method. The SIP Header class 220 contains aHeader attribute and a Content attribute which define a SPT for thepresence or absence of any SIP header or for the content of any SIPheader. The Session Case class 222 is an enumerated type, with possiblevalues “Originating”, “Terminating_Registered”,“Terminating_Unregistered”, “Originating_Unregistered” which indicatewhether the filter should be used by the S-CSCF 110 handling theOriginating, Terminating for a registered end user 114, Terminating foran unregistered end user 114, or Originating for an unregistered enduser 114. The Session Description Information class 224 has a Lineattribute and a Content attribute which define a SPT for the content ofany SDP field within the body of a SIP Method.

In view of FIGS. 2A-2C (PRIOR ART), it can be seen that the serviceprofile 116 has one or more IFCs 206′ which are the mechanism that isdownloaded to and then used by the S-CSCF 110 in the IMS Core 108 toinvoke an IMS service for the UE 114 (only one shown). Basically, theIFCs 206′ identify the particular IMS application server 112 that has tobe invoked by the S-CSCF 110 and what must be done if that particularINS application server 112 is not available. In addition, the IFCs 206′include one or more SPTs 214 which specify under which conditions theidentified IMS application server 112 shall be involved in a SIP sessionsuch that the IMS service can be invoked for the particular UE 114.

In particular, the S-CSCF 110 when handling a SIP request for the UE 114(or the IMS application server 112 on behalf of the UE 114) goes throughthe list of prioritized IFCs 206 and the corresponding SPTs 214 withinthe service profile 106. And, when the conditions in the IFCs 206 andthe corresponding SPTs 214 are satisfied according to the information inthe SIP request then the S-CSCF 110 contacts the IMS application server112 that was indicated in the Application Server class 212 to invoke theSIP request. Generally speaking, the IFCs 206 are related to SIPmessages and SIP procedures and, consequently, the conditions specifiedin the corresponding SPTs 214 are also related to the contents of theSIP messages and the SIP procedures. This can be seen by the fact thatthe SPTs 214 which have been standardized to date include theRequest-URI 218, the SIP Method 216 (e.g. INVITE), the SIP Header 220(for the presence or absence of any SIP header or for the content of anySIP header), the Session Case 222 (an enumerated type, with possiblevalues “Originating”, “Terminating_Registered”,“Terminating_Unregistered”, “Originating_Unregistered”), and the SessionDescription 224 (for the content of any SDP field located within thebody of a SIP Method) (note: SDP is a format for describing streamingmedia initialization parameters and is discussed in detail within IETF'sRFC 4566).

However, there is high interest today to take into account otherinformation and not only SIP information that is related to the specificSIP request which is received by the S-CSCF 110 to invoke an IMS servicefor the UE 114. For example, today it is not possible to take intoaccount the CS status (GSM attached, etc. . . . ) of the UE 114 todecide whether one IMS application server 112 or another IMS applicationserver should be involved in the SIP request. Accordingly, there hasbeen and is a need to address this shortcoming and other shortcomingswith the current state-of-the-art when invoking an IMS service for aparticular UE. This need and other needs are satisfied by the presentinvention.

SUMMARY

In one aspect, the present invention provides a server that includes adatabase that stores a service profile for the user, where the serviceprofile has a number of filter criteria, wherein at least one includes:(1) a first trigger point and at least one first service point triggerthat specifies one or more conditions which when satisfied will bedownloaded to and checked by a remote control function before a serviceis invoked for the user-user equipment; and (2) a second trigger pointand at least one second service point trigger that specifies one or moreconditions which are checked against internally stored data (e.g.,non-SIP related data) associated with the user-user equipment and whichneed to be satisfied before the service profile with the filter criteriaincluding the first trigger point and the at least one first: servicepoint trigger is downloaded to and checked by the remote controlfunction to invoke the service for the user-user equipment. This schemeis desirable since the server can use internally stored non-SIP relatedinformation when invoking a service for the user-user equipment. Plus,this scheme is desirable since the server can influence the invoking ofthe service by using the second trigger point and the internally storednon-SIP related data to determine if the first trigger point should bedownloaded in the first place to the remote control function which thenmay invoke the service for the user-user equipment.

In another aspect, the present invention provides a method for enablinga server to influence an invoking of a service to a user-user equipment.The method comprising the steps of: (a) creating a service profile forthe user-user equipment, where the service profile has a number offilter criteria, wherein at least one includes: (1) a first triggerpoint and at least one first service point trigger that specifies one ormore conditions which have to be satisfied before a remote controlfunction can invoke the service for the user-user equipment; and (2) asecond trigger point and at least one second service point trigger thatspecifies one or more conditions which will be checked againstinternally stored data that is associated with the user-user equipment;(b) pre-filtering the filter criteria by determining if there is a matchbetween the one or more conditions in the at least one second servicepoint trigger and the internally stored data that is associated with theuser-user equipment; (c) if there is a match, then downloading theservice profile with the filter criteria including the first triggerpoint and the at least one first service point trigger to the remotecontrol function, wherein the remote control function then needs toconfirm that the one or more conditions of the at least one firstservice point trigger are satisfied before invoking the service for theuser-user equipment; and (d) if there is not a match, then preventingthe download of the service profile with the filter criteria includingthe first trigger point and the at least one first service point triggerto the remote control function.

In yet another aspect, the present invention provides a 3GPP networkwhich includes a HSS, a S-CSCF, and an IMS Application Server, whereinthe HSS influences an invoking of an IMS service provided by said IMSApplication Server to a user-user equipment by: (a) creating a serviceprofile for the user-user equipment, where the service profile has anInitial Filter Criteria (IFC) that includes: (1) a first trigger pointand at least one first service point trigger that specifies one or moreconditions which have to be satisfied before the S-CSCF can invoke theIMS service for the user-user equipment; and (2) a second trigger pointand at least one second service point trigger that specifies one or moreconditions which will be checked against internally stored data that isassociated with the user-user equipment; (b) pre-filtering the IFC bydetermining if there is a match between the one or more conditions inthe at least one second service point trigger and the internally storeddata that is associated with the user-user equipment; (c) if there is amatch, then downloading the service profile with the IFC including thefirst trigger point and the at least one first service point trigger tothe S-CSCF, wherein the S-CSCF then has to confirm that the one or moreconditions of the at least one first service point trigger are satisfiedbefore invoking the IMS Application Server to provide the IMS servicefor the user-user equipment; and (d) if there is not a match, thenpreventing the download of the service profile with the IFC includingthe first trigger point and the at least one first service point triggerto the S-CSCF.

Additional aspects of the invention will be set forth, in part, in thedetailed description, figures and any claims which follow, and in partwill be derived from the detailed description, or can be learned bypractice of the invention. It is to be understood that both theforegoing general description and the following detailed description areexemplary and explanatory only and are not restrictive of the inventionas disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the present invention may be obtainedby reference to the following detailed description when taken inconjunction with the accompanying drawings:

FIG. 1 (PRIOR ART) is a diagram illustrating a 3GPP network which has atraditional HSS coupled to a CS domain, a PS domain and an IM CNsubsystem as currently specified in 3GPP TS 29.228 V7.5.0;

FIGS. 2A-2C (PRIOR ART) are diagrams illustrating an outline of a UMLmodel for the traditional service profile that is currently specified in3GPP TS 29.228 V7.5.0;

FIG. 3 is a diagram illustrating a 3GPP network which has an enhancedHSS that is coupled to a CS domain, a PS domain and an IM CN subsystemin accordance with the present invention;

FIGS. 4A-4C are three diagrams illustrating an outline of an UML modelfor an exemplary service profile that is configured in accordance withthe present invention;

FIG. 5 is a signal flow diagram illustrating how the enhanced HSS can beused during the registration of a UE in accordance with the presentinvention;

FIG. 6 is a signal flow diagram illustrating how the enhanced HSS can beused during a termination session towards a UE in accordance with thepresent invention; and

FIG. 7 is a signal flow diagram illustrating how the enhanced HSS can beused when there is a change in the data for the UE in accordance withthe present invention.

DETAILED DESCRIPTION

Referring to FIG. 3, there is a diagram illustrating a 3GPP network 300which has an enhanced HSS 302 that is coupled to a CS domain 304, a PSdomain 306 and an IM CN subsystem 308 in accordance with the presentinvention. The enhanced HSS 302 has a master database 303 for UEs 314(only one shown) which supports HLR functions as well as IMS relatedsubscription and subscriber data. The enhanced HSS 302 also handles aservice profile 316 for each IMS UE 314 and, during registration of agiven UE 314, submits the corresponding service profile 316 towards anS-CSCF 310 (located in IM CN subsystem 308) that is assigned to servethe given UE 314. For the sake of simplicity, user and user equipmentare generally referred to as the same and have often been identified asUE 314 throughout the present document, so that the information storedin the master database 303 on a user basis is generally referred to asuser data irrespective of whether such data is associated with the useror their respective user equipment.

As in the past, the enhanced HSS 302 still handles a service profile 316that includes the traditional IFCs which are used by the S-CSCF 310 toinvoke IMS services executed in an IMS Application Server 312 for theuser and their respective UE 314. Each traditional IFC, in a serviceprofile 316 for a given UE 314, includes a plurality of SPTs thatspecify conditions that need to be satisfied before the S-CSCF 310involves an IMS application server 312 in the invocation of IMS servicesfor the given UE 314. The traditional IFC's are related to SIP messagesand SIP procedures and, consequently, the conditions specified bycorresponding SPT's are also related to the contents of the SIP messagesand the SIP procedures. However, the service profile 316 has also beenchanged so that other information and not only SIP information that isrelated to a specific SIP request received by the S-CSCF 110 can betaken into account to influence the invoking of an IMS service for agiven UE 314. For example, the other information can include data suchas whether or not the CS status is active for the given UE 314, theIP-CAN where the given UE 314 has accessed the IMS network 208, the typeof PS network 306 accessed by the given UE 314 etc. . . . The enhancedHSS 302 has access to this non-SIP related information since it is themaster database for the 3GPP network 300.

In particular, the enhanced HSS 302 in accordance with the presentinvention provides for a service profile 316 which has an enhanced IFCpackage that, in addition to the traditional IFC's (includingSIP-related SPTs), further includes what are called herein asHSS-Trigger Points (HSS-TPs). Each HSS-TP includes pre-filter conditionsthat are checked by the enhanced HSS 302 against relevant subscriberdata (e.g., non-SIP related information) to determine which if any ofthe IFC's configured for the given UE 314 will be downloaded and furtherevaluated by the assigned S-CSCF 310.

A detailed discussion is provided below to explain how the serviceprofile 316 is expanded to include the new HSS-TPs and then a discussionis provided to explain how the enhanced HSS 302 operates to influencethe invoking of an IMS service for a given UE 314 by using the newHSS-TPs to determine which IFCs in the service profile 316 will bedownloaded to the assigned S-CSCF 310.

Referring to FIGS. 4A-4C, there are three diagrams illustrating anoutline of an UML model for an exemplary service profile 316 that isconfigured in accordance with the present invention. FIG. 4A illustratesa high level of the exemplary service profile 316 which has thefollowing: (1) a Public Identification class 402; (2) a Core NetworkService Authorization class 404; (3) an enhanced Initial Filter Criteriaclass 406; and (4) a Shared IFC Set class 408. The service profile 316includes the enhanced IFC class 406 which is described in detail belowand also uses the previously standardized Public Identification class402, the Core Network Service Authorization class 404, and the SharedIFC Set class 408 (compare to FIG. 2A).

FIG. 4B is a diagram illustrating an outline of the UML model of theenhanced IFC class 406 in accordance with the present invention. Theenhanced IFC class 406 has zero to n IFC instances 406′ (one shown) eachof which has a priority attribute that indicates the priority of thefilter criteria where the higher the priority number is then the lowerthe priority of the filter criteria. For example, an IFC 406′ with ahigher value of priority number would be assessed after the IFC 406′with a smaller priority number has been assessed. Plus, each IFC 406′has a ProfilePartIndicator attribute that is an enumerated type, withpossible values “REGISTERED and UNREGISTERED, which indicates if therespective filter is a part of the registered or unregistered userservice profile 316.

In addition, each IFC instance 406′ is composed of zero or one instanceof a Trigger Point class 410, one instance of an Application Serverclass 412, and one instance of a HSS-trigger point 414 including one ormore HSS-owned SPT(s) 416. In particular, each IFC 406′ has thestandardized Trigger Point class 410 (including the corresponding SPT418), the standardized Application Server class 412 (including thecorresponding Service Information 417), and the new HSS-trigger point414 which has the corresponding HSS-owned SPTs 416 (compare to FIG. 2B).The SPT 418 has one to n SPT instances 418′ one of which is shown indetail in FIG. 4C and includes the following: (1) Request-URI class 420;(2) SIP Method class 422; (3) SIP Header class 424; (4) Session Caseclass 426; and (5) Session Description class 428 (compare to FIG. 2C).

As shown in FIG. 4B, the HSS-trigger point 414 is composed of 1 to ninstances of the HSS-owned SPTs 416. Plus, each HSS-trigger point 414 isa boolean expression in Conjunctive or Disjunctive Normal form (CNF ofDNF). More specifically, each HSS-trigger point 414 has aConditionTypeCNF attribute that defines how the set of correspondingHSS-owned SPTs 416 are expressed, i.e. either an ORed set of ANDed setsof SPT statements or an ANDed set of ORed sets of statements. Thesecombinations are termed, respectively, Disjunctive Normal Form (DNF) andConjunctive Normal Form (CNF). Both DNF and CNF forms can be used.

In operation, the enhanced HSS 302 during UE 314's registration (forexample) checks each IFC 406′ and their corresponding HSS-trigger point414 and associated HSS-owned SPTs 416 to determine if the correspondingTrigger point class 410 and Application Server class 412 will bedownloaded to the S-CSCF 310. In particular, the enhanced HSS 302 has anevaluation process that checks the conditions stated in the HSS-ownedSPTs 416 against internally stored non-SIP related user data. If thereis a match, then the enhanced HSS 302 downloads the service profile 316with the corresponding IFC 406′ (absent the HSS-trigger point 414 andthe associated HSS-owned SPTs 416) to the S-CSCF 310. If there is not amatch, then the enhanced HSS 302 downloads the service profile 316without the corresponding IFC 406′ to the S-CSCF 310. Upon receiving theservice profile 316, the S-CSCF 310 goes through the received IFCs 406′and their corresponding SPTs 418 and when the conditions in the IFCs406′ and the corresponding SPTs 418 are satisfied according to theinformation in a pending SIP request then the S-CSCF 310 contacts theappropriate IMS application server 312 to invoke the SIP request andprovides IMS service to the UE 314. In this way, the enhanced HSS 302 isable to influence the invoking of the IMS service provided by an IMSapplication server 312 to the UE 314.

As can be seen, the enhanced HSS 302 includes in each IFC 406′ acombination of a new type of SPTs called HSS-owned SPTs 416 that are notdownloaded to the S-CSCF 310 but instead are first evaluated in theenhanced HSS 302. In this evaluation process, the enhanced HSS 302determines if the conditions in the HSS owned SPTs 416 are satisfied inview of non-SIP related information and if yes then the correspondingIFCs 406′ will be downloaded to the S-CSCF 310 and if not then thecorresponding IFCs 406′ will not be downloaded to the S-CSCF 310. In onepossible application, assume according to the HSS owned SPTs 416 of oneIFC 406′ that the UE 314 needs to be in CS status=GSM attach for thatIFC 406′ to apply, then only if that is the case, will that IFC 406′ besent down to the S-CSCF 310. If the UE 314 is not GSM attached, thenfrom the IMS core perspective 308 that particular IFC 406′ was neverpart of the user service profile 316. Some additional examples ofnon-SIP related data that can be used to check conditions in HSS-ownedSPTs 416 include user data related to an IP-CAN accessed by the UE 314,the PS network 106 accessed by the UE 314, the user location overdifferent accesses etc. It is important to remark that the enhanced HSS302 is a privileged point in the 3GPP network 300 where the manydifferent accesses meet, and so it already stores a lot of valuableinformation (non-SIP related information) about the UE 314 which couldbe used in the evaluation process.

The enhanced HSS 302 behavior where the HSS-owned SPTs 416 are evaluatedusing non-SIP related information is beneficial in many different IMSprocedures. Several examples of which are as follows:

-   -   At user registration: the IFCs 406′ having the HSS-owned SPTs        416 will be evaluated by the enhanced HSS 302, and downloaded to        the S-CSCF 310 only if their conditions are met according to        HSS's knowledge of the UE 314 (see FIG. 5).    -   At a terminating session towards a not registered user: The        enhanced HSS 302 answer to a location information request will        be such that the S-CSCF 310 assignment will proceed only if        there is at least one IFC 406′ left that is applicable to the        user's “unregistered status” after the HSS-owned SPTs 416 have        been evaluated (see FIG. 6).    -   At a change of user dynamic data relevant for HSS-owned SPTs 416        or at a change of the user service profile 316 by provisioning:        The enhanced HSS 302 evaluation of HSS-owned SPTs 416 may lead        to the download of the service profile 316 to the S-CSCF 310        only if there are any changes when compared with the previously        downloaded user service profile 316 (see FIG. 7).

Referring to FIG. 5, there is a signal flow diagram illustrating how theenhanced HSS 302 can be used during the registration of a UE 314 inaccordance with the present invention. The steps are as follows:

1. UE 314 (UE A) uses the VMSC to register in CS with the enhanced HSS302.

2. UE 314 (UE A) starts an INS registration request with the S-CSCF 310.

3. The S-CSCF 310 sends a SAR message to the enhanced HSS 302.

4. The enhanced HSS 302 uses non-SIP related information to evaluate (orpre-filter) the HSS-owned SPTs 416 in the service profile 316 associatedwith UE 314. In this case, the UE 314 registration status in the CSaccess will be taken into account during the evaluation of the HSS-ownedSPTs 416 in the service profile 316.

5. The enhanced HSS 302 downloads a SAA message (including UE 314'sservice profile 316 with applicable IFCs 406′ based on the result ofstep 4) to the S-CSCF 310.

6. UE 314 (UE A) registers with the S-CSCF 310.

Referring to FIG. 6, there is a signal flow diagram illustrating how theenhanced HSS 302 can be used during a terminating session towards UE 314in accordance with the present invention. The steps are as follows:

1. UE 314 (UE A) uses the VMSC to register in CS with the enhanced HSS302.

2. UE B sends a SIP INVITE to the S-CSCF 310 to establish a session withUE 314. More precisely, this SIP INVITE message is not directlysubmitted from UE B towards the S-CSCF 310 but is rather submittedthrough other network nodes that have not depicted for the sake ofsimplicity, since they are not relevant to the present discussion.

3. The S-CSCF 310 sends a SAR message to the enhanced HSS 302. At thistime, UE 314 is not registered in IMS but is attached to CS (step 1).

4. The enhanced HSS 302 uses non-SIP related information to evaluate (orpre-filter) the HSS-owned SPTs 416 in the service profile 316 associatedwith UE 314. In this case, the UE 314 registration status in the CSaccess will be taken into account during the evaluation of the HSS-ownedSPTs 416 in the service profile 316.

5. The enhanced HSS 302 downloads a SAA message (including UE 314'sservice profile 316 with applicable IFCs 406′ based on the result ofstep 4) to the S-CSCF 310. This service profile 316 will be used toestablish a session between UE B and UE 314.

Note: there is another possible outcome in this termination session casewhich is that, after the HSS-owned SPTs have been evaluated (step 4),there is not even one IFC 416′ left that is applicable to the UE 314when in “unregistered status”. If this is the case, then the enhancedHSS 302 answer to the received request (step 5) will indicate this andthe session establishment will not progress.

Referring to FIG. 7, there is a signal flow diagram illustrating how theenhanced HSS 302 can be used when there is a change in the data for theUE 314 in accordance with the present invention. The steps are asfollows:

1. UE 314 (UE A) uses the VMSC to register in CS with the enhanced HSS302.

2. UE 314 (UE A) starts an IMS registration request with the assignedS-CSCF 310.

3. The S-CSCF 310 sends a SAR message to the enhanced HSS 302.

4. The enhanced HSS 302 uses non-SIP related information to evaluate (orpre-filter) the HSS-owned SPTs 416 in the service profile 316 associatedwith UE 314. In this case, the UE 314 registration status in the CSaccess will be taken into account during the evaluation of the HSS-ownedSPTs 416 in the service profile 316.

5. The enhanced HSS 302 downloads a SAA message (including UE 314'sservice profile 316 with applicable IFCs 406′ based on the result ofstep 4) to the S-CSCF 310.

6. UE 314 (UE A) registers with the S-CSCF 310.

7. UE 314 (UE A) detaches from CS which means that the UE 314 status haschanged relative to the CS status that was stored in the enhanced HSS302 and used in step 4.

8. The enhanced HSS 302 re-evaluates the HSS-owned SPTs 416 in UE 314'sservice profile 316 because the UE 314 status relative to CS attachmenthad changed from attached CS to detached CS.

9. The enhanced HSS 302 downloads a PPR message (including UE 314'sservice profile 316 with applicable IFCs 406′ (if any) based on theresult of step 8) to the S-CSCF 310.

10. The S-CSCF 310 responds by sending a PPA message back to theenhanced HSS 302.

In an alternative embodiment, the mechanism is that new SPTs are addedto the existing SPTs 418 so the trigger points 410 include conditionsrelated to HSS stored user information, and that, instead of evaluatingthese new SPTs in the enhanced HSS 302 (as described above), the S-CSCF310 receives all of this information in real-time download from theenhanced HSS 302. In particular, the enhanced HSS 302 would download tothe S-CSCF 310 all of the IFCs and all of the non-SIP related userinformation (e.g. user CS status), so that this non-related SIPinformation can be considered by the S-CSCF 310 during the IFCevaluation. However, this alternative embodiment would have somedrawbacks:

-   -   1. It would require additional parameters both in the user        service profile 316 but also on the Cx (see FIG. 3), which        implies a high effort to get this particular embodiment        standardized.    -   2. The operators will most likely want to make use of other        information related to user status and location on other        accesses and not just for IMS access. If this happens, then this        particular embodiment would also need a standardization effort        for each of these different accesses.    -   3. The particular embodiment is not optimized for the Cx        signaling or the S-CSCF 310 storage because (for example):        -   The HSS 302 would be, in some cases, informing the S-CSCF            310 about user data and user data changes that are not            applicable to a specific user.        -   The HSS 302 would be, in some cases, downloading IFCs to the            S-CSCF 310 that may not apply at all during the registration            life of the user.        -   The non-SIP related user data stored in the HSS 302 would            have to be duplicated, as it now would need to be downloaded            and synchronized in the S-CSCF 310.

In comparison, the first embodiment of the present invention where theenhanced HSS 302 does not download the non-SIP related to the S-CSCF 310is considered a better solution since the IMS core 308 still takes intoaccount the HSS stored user information albeit indirectly for serviceinvocation while at the same time optimizing the usage of both thesignaling interface Cx and the data storage (memory capacity) in theS-CSCF 310. Plus, the first embodiment of the present invention isdesirable since the current 3GPP standards specify which HSS-ownedinformation the vendors need to support to state compliance with aspecific release. Thus, the first embodiment of the present inventionenables vendor differentiation where particular vendors can create theirown HSS-Owned SPTs 416 without interoperability problems and without anyadditional standardization since the HSS-Owned SPTs 416 would only beknown to the enhanced HSS 302.

In summary, it should be appreciated that the first embodiment of thepresent solution discussed herein provides an efficient and extensiblemechanism that allows HSS stored user information (both user dynamic butalso user provisioned data) to be taken into account during the IFCevaluation process, and in this way influence the invoked services forthe corresponding user. The enhanced HSS does this by adding HSS-ownedSPTs to the IFCs information and performing a pre-filter of the IFCsthemselves based on non-SIP related user data that is also stored in theHSS. As a result of this pre-filter step, the IFC will or will not bedownloaded to the S-CSCF. In this way, the HSS is able to influence theinvoked IMS services that are provided to a user by using stored userdata.

Although several embodiments of the present invention have beenillustrated in the accompanying Drawings and described in the foregoingDetailed Description, it should be understood that the invention is notlimited to the disclosed embodiments, but instead is also capable ofnumerous rearrangements, modifications and substitutions withoutdeparting from the spirit of the invention as set forth and defined bythe following claims.

1. A server, comprising: a database that stores a service profile for auser-user equipment, where the service profile has a number of filtercriteria wherein at least one includes: a first trigger point and atleast one first service point trigger that specifies one or moreconditions which when satisfied will be downloaded to and checked by aremote control function before a service is invoked for the user-userequipment; and a second trigger point and at least one second servicepoint trigger that specifies one or more conditions which are checkedagainst internally stored data associated with the user-user equipmentand need to be satisfied before the service profile with the filtercriteria including the first trigger point and the at least one firstservice point trigger is downloaded to and then checked by the remotecontrol function to invoke the service for the user-user equipment. 2.The server of claim 1, wherein said at least one first service pointtrigger further includes: a request Uniform Resource Indicator (URI); aSession Initiation Protocol (SIP) Method; a Session Initiation Protocol(SIP) Header; a Session Case; or a Session Description.
 3. The server ofclaim 1, wherein said internally stored data is non-Session InitiationProtocol (SIP) related data including: a Circuit Switch (CS) status ofthe user-user equipment; an IP Connectivity Access Network (IP-CAN)accessed by the user-user equipment; or a type of Packet Switch (PS)network accessed by the user-user equipment.
 4. The server of claim 1,wherein the at least one second service point trigger has a booleanexpression in Conjunctive Normal Form, CNF, or in Disjunctive NormalForm, DNF, that specifies the one or more conditions which are to bechecked against the internally stored data associated with the user-userequipment.
 5. A method for enabling a server to influence an invoking ofa service to a user-user equipment, said method comprising the steps of:creating a service profile for the user-user equipment, where theservice profile has a number of filter criteria wherein at least oneincludes: a first trigger point and at least one first service pointtrigger that specifies one or more conditions which have to be satisfiedbefore a remote control function can invoke the service for theuser-user equipment; and a second trigger point and at least one secondservice point trigger that specifies one or more conditions which willbe checked against internally stored data that is associated with theuser-user equipment; pre-filtering the filter criteria by determining ifthere is a match between the one or more conditions in the at least onesecond service point trigger and the internally stored data that isassociated with the user-user equipment; if there is a match, thendownloading the service profile with the filter criteria including thefirst trigger point and the at least one first service point trigger tothe remote control function, wherein the remote control function thenneeds to confirm that the one or more conditions of the at least onefirst service point trigger are satisfied before invoking the servicefor the user-user equipment; and if there is not a match, thenpreventing the download of the service profile with the filter criteriaincluding the first trigger point and the at least one first servicepoint trigger to the remote control function.
 6. The method of claim 5,wherein said pre-filtering step is performed when the user-userequipment registers with the remote control function.
 7. The method ofclaim 5, wherein said pre-filtering step is performed when anotheruser-user equipment attempts to terminate a session with the user-userequipment.
 8. The method of claim 5, wherein said pre-filtering step isperformed after provisioning the service profile of the user-userequipment.
 9. The method of claim 5, wherein said pre-filtering step isperformed after a change in the internally stored data associated withthe user-user equipment.
 10. The method of claim 5, wherein said serveris a Home Subscriber Server, HSS, which is used within a 3GPP network.11. The method of claim 5, wherein the filter criteria is an InitialFilter Criteria, IFC, which is used within a 3GPP network.
 12. Themethod of claim 5, wherein said remote control function is a ServingCall Session Control Function, S-CSCF, which is used within a 3GPPnetwork.
 13. The method of claim 5, wherein said at least one firstservice point triggers further includes: a request Uniform ResourceIndicator (URI); a Session Initiation Protocol (SIP) Method; a SessionInitiation Protocol (SIP) Header; a Session Case; or a SessionDescription.
 14. The method of claim 5, wherein said internally storeddata is non-Session Initiation Protocol (SIP) related data including: aCircuit Switch (CS) status of the user-user equipment; an IPConnectivity Access Network (IP-CAN) accessed by the user-userequipment; or a type of Packet Switch (PS) network accessed by theuser-user equipment.
 15. The method of claim 5, wherein the at least onesecond service point trigger has a boolean expression in ConjunctiveNormal Form, CNF, or in Disjunctive Normal Form, DNF, that specifies theone or more conditions which are to be checked against the internallystored data associated with the user-user equipment.
 16. A 3GPP network,comprising: a Home Subscriber Server (HSS); a Serving Call SessionControl Function (S-CSCF); an IMS Application Server, wherein the HSSinfluences an invoking of an IMS service provided by said IMSApplication Server to a user-user equipment by: creating a serviceprofile for the user-user equipment, where the service profile has anumber of Initial Filter Criteria (IFC) wherein at least one includes: afirst trigger point and at least one first service point trigger thatspecifies one or more conditions which have to be satisfied before theCSCF invokes the IMS service for the user-user equipment; and a secondtrigger point and at least one second service point trigger thatspecifies one or more conditions which will be checked againstinternally stored data that is associated with the user-user equipment;pre-filtering the IFC by determining if there is a match between the oneor more conditions in the at least one second service point trigger andthe internally stored data that is associated with the user-userequipment; if there is a match, then downloading the service profilewith the IFC including the first trigger point and the at least onefirst service point trigger to the S-CSCF, wherein the S-CSCF then hasto confirm that the one or more conditions of the at least one firstservice point trigger are satisfied before invoking the IMS ApplicationServer to provide the IMS service for the user-user equipment; and ifthere is not a match, then preventing the download of the serviceprofile with the IFC including the first trigger point and the at leastone first service point trigger to the S-CSCF.
 17. The 3GPP network ofclaim 16, wherein said at least one first service point trigger furtherincludes: a request Uniform Resource Indicator (URI); a SessionInitiation Protocol (SIP) Method; a Session Initiation Protocol (SIP)Header; a Session Case; or a Session Description.
 18. The 3GPP networkof claim 16, wherein said internally stored data is non-SessionInitiation Protocol (SIP) related data including: a Circuit Switch (CS)status of the user-user equipment; an IP Connectivity Access Network(IP-CAN) accessed by the user-user equipment; or a type of Packet Switch(PS) network accessed by the user-user equipment.
 19. The 3GPP networkof claim 16, wherein the at least one second service point trigger has aboolean expression in Conjunctive Normal Form, CNF, or in DisjunctiveNormal Form, DNF, that specifies the one or more conditions which are tobe checked against the internally stored data associated with theuser-user equipment.